Packet data
3.13.4 Concurrent Services: Call Clearing Examples
h. The MSC sends an Assignment Request message to the Target BS to request
4
assignment of radio resources. The MSC starts timer T10.
5
i. Upon receipt of the Assignment Request message from the MSC, the Target
6
BS stops timer T303.
7
j. The Target BS may send a Call Assignment Message over the traffic channel
8
of the radio interface to initiate the establishment of a CC state machine.
9
k. The Target BS sends either the Service Connect Message, the General
10
Handoff Direction Message or the Universal Handoff Direction Message to
11
the MS to invoke the additional service option connection.
12
l. The MS responds with a Service Connect Completion Message through
13
service negotiation procedure.
14
m. The Target BS sends an A9-Setup-A8 message over the A9 (Signaling)
15
connection to the PCF to establish an A8 (User Traffic) connection between
16
Target BS and the PCF. The Target BS then starts timer TA8-Setup.
17
n. The PCF responds with an A9-Connect-A8 message to complete the setup of
18
the A8 (User Traffic) connection for the packet service request. Upon receipt
19
of the A9-Connect-A8 message from the PCF, the Target BS stops timer T
A8-20
Setup.
21
o. After the radio link and the A8 connection have been established, the Target
22
BS sends an Assignment Complete message to the MSC. The MSC stops
23
timer T10.
24
3.13.4 Concurrent Services: Call Clearing Examples
25
3.13.4.1 Call Clear via Service Release – MS Initiated
26
This section describes the call flow associated with a single service option connection
27
release initiated by MS from the two active service option connections in the system.
28
MS MSC
time comment
SreqM/RRRM/RRRMM
a b c d Service Release
Service Release Complete SCM/GHDM/UHDM
T308 BS
Concurrent Service active
Service Connect Completion
Service Negotiation
e
1
Figure 3.13.4.1-1 Releasing a Service that is not the Only one
2
Connected (MS Initiated)
3
a. The mobile station may send one of the Service Request Message, Resource
4
Release Request Message or Resource Release Request Mini Message
5
(RRRMM) for releasing a service that is not the only service connected to the
6
MS.
7
b. The BS then sends the Service Release message to the MSC to clear a call
8
control transaction associated with the service. Timer T308 is started by the
9
BS.
10
c. Upon receiving the Service Release Message from the BS, the MSC releases
11
the service option connection identifier, the terrestrial circuit, if allocated for
12
the associated service, and sends a Service Release Complete Message to the
13
BS. Upon receipt of the Service Release Complete Message, the BS stops
14
Timer T308.
15
d. Upon receiving the Service Release Complete message, the BS shall go to the
16
“null” state for the service option connection identifier, release the radio
17
resource for the associated service option connection identifier and then may
18
transmit one of the Service Connect Message, General Handoff Direction
19
Message or Universal Handoff Direction Message to the MS.
20
e. The MS responds with a Service Connect Completion Message through
21
service negotiation procedure.
22
3.13.4.2 Call Clear via Service Release - MSC Initiated
23
This section describes the call flow associated with a single service option connection
24
release initiated by MSC from the two active service option connections in thesystem.
25
MS MSC
time comment
a b
c d Service Release
Service Release Complete SCM/GHDM/UHDM
T308 BS
Concurrent Service active
Service Connect Completion
Service Negotiation
1
Figure 3.13.4.2-1 Releasing a service that is not the only one
2
connected (MSC initiated)
3
a. The MSC sends a Service Release message to the BS to instruct the BS to
4
release a call control transaction associated with the service and starts timer
5
T308.
6
b. The BS sends one of the Service Connect Message, General Handoff
7
Direction Message or Universal Handoff Direction Message to the MS to
8
release the associated service option connection.
9
c. The MS responds with a Service Connect Completion Message through
10
service negotiation procedure.
11
d. The BS releases the service option connection identifier, the terrestrial circuit,
12
if allocated for the associated service and sends a Service Release Complete
13
Message to the MSC. Upon receipt of the Service Release Complete, the MSC
14
stops timer T308.
15
3.13.5 Concurrent Service - Handoff
16
This section describes the handoff call flows for concurrent service.
17
3.13.5.1 Concurrent Service (active voice and packet data services) - Hard Handoff
18
This section describes call flows for the successful hard handoff of a mobile that is
19
engaged in active voice and packet data calls simultaneously.
20
3.13.5.1.1 Successful Inter-BS Hard Handoff Call Flows (within the same PCF)
21
The call flows in this section are identical to the call flows described in Section
22
3.11.4.2.14.
23
3.13.5.1.2 Successful Inter-PCF Hard Handoff Call Flows (mobile served by the same
1
PDSN)
2
The call flows in this section are identical to the call flows described in Section
3
3.11.4.2.15 and Section 3.11.5.5.10.
4
3.13.5.1.3 Successful Inter-PCF Hard Handoff Call Flows (mobile served by new PDSN)
5
The call flows in this section are identical to the call flows described in Section
6
3.11.5.5.11.
7
3.13.5.2 Concurrent Service (active voice and dormant packet data services) - Handoff
8
This section describes call flows for the successful handoff of a mobile that is engaged in
9
an active voice call and has a dormant packet data session.
10
3.13.5.2.1 Successful Inter-PCF Handoff Call Flows (mobile served by the same PDSN)
11
This section describes the call flows for the successful handoff between PCFs being
12
served by the same PDSN of a mobile that is engaged in an active voice call and has a
13
dormant packet data session. It is assumed that the PCFs are in different packet zones,
14
and that the call is not in inter-BS soft/softer handoff prior to the hard handoff, and thus
15
no A3 connections need to be removed.
16
X
Time Comment
a b c d e f g
h i
PDSN Dormant HO
j k l
MS Source Target MSC Source
PCF
Target
PCF PDSN
Handoff Request Handoff Required
Handoff Request Ack
T11
Handoff Command T7
Handoff Direction Message
Null Forward Traffic frames
MS Ack Order
Twaitho
Handoff Commenced Reverse Traffic frames or traffic preamble
Handoff Completion Message
BS Ack Order
Handoff Complete T9
Clear Command Clear Complete T306
T315
Enhanced Origination Message
BS Ack Order
Additional Service Request
Assignment Request T303
A9-Setup-A8
TA8-Setup
Assignment Failure
A9-Release-A8 Complete T10
Service Release Service Release Complete
T20
T308
m n o p q
r
s
t
u
v
w x y
In Traffic System Parameter Message
Active Voice Session, Dormant Packet Data Session z
1
Figure 3.13.5.2.1-1 Successful Inter-PCF Handoff (mobile served
2
by the same PDSN)
3
a. The MS currently has a voice call active and a packet data service that is
1
dormant. Based on an MS report that it crossed a network specified threshold
2
for signal strength or for other reasons, the source BS recommends a hard
3
handoff to one or more cells in the domain of the target BS. The source BS
4
sends a Handoff Required message with the list of cells to the MSC and starts
5
timer T7.
6
b. The MSC sends a Handoff Request message to the target BS with the IS2000
7
Channel Identity element present since the hard handoff bit was set and/or the
8
Handoff Type element in the Handoff Required message indicated hard
9
handoff. The MSC starts timer T11.
10
c. Upon receipt of the Handoff Request message from the MSC, the target BS
11
allocates appropriate radio resources as specified in the message and connects
12
the call. As the HO Request message can have multiple cells specified, the
13
target BS can also choose to setup multiple cells for the handoff request The
14
target BS sends null forward traffic channel frames to the MS.
15
d. The target BS sends a Handoff Request Acknowledge message to the MSC.
16
The target BS starts timer T9 to wait for arrival of the MS on its radio channel.
17
The first cell in the cell identifier list element of the message will be treated as
18
the new designated cell by the MSC. The change of designated cell occurs
19
upon receipt of the HO Complete message.
20
If the service option received in the Handoff Request message is not available
21
at the target BS and the target BS selected a different service option for the
22
handoff then the target BS shall include the service option it selected in the
23
Service Configuration Record IE.
24
e. Upon receipt of the Handoff Request Acknowledge message the MSC stops
25
timer T11. The MSC prepares to switch from the source BS to the target BS
26
and sends a Handoff Command to the source BS. The source BS stops timer
27
T7. The MSC shall include the service option it received from the Handoff
28
Request Acknowledgement message in the Handoff Command message.
29
f. The source BS sends the handoff direction message1 to the MS across the air
30
interface. If the MS is allowed to return to the source BS, then timer Twaitho is
31
also started by the source BS.
32
g. The MS may acknowledge the handoff direction message by sending a MS
33
Ack Order to the source BS.
34
If the handoff direction message is sent using quick repeats, the source BS
35
might not request an acknowledgment from the MS.
36
h. The source BS sends a Handoff Commenced message to the MSC to notify it
37
that the MS has been ordered to move to the target BS channel. The source BS
38
starts timer T306 to await the Clear Command message from the MSC. If timer
39
Twaitho has been started, the source BS shall wait for that timer to expire
40
before sending the Handoff Commenced message.
41
i. The MS sends reverse traffic channel frames or the traffic channel preamble to
42
the target BS.
43
1 This may be a Handoff Direction Message, a General Handoff Direction Message, an Extended Handoff Direction Message, or a Universal Handoff Direction Message as appropriate.
j. Upon acquisition of the traffic channel, the MS sends a Handoff Completion
1
Message to the target BS.
2
k. The target BS sends the BS Ack Order to the MS over the air interface.
3
l. The target BS sends a Handoff Complete message to the MSC to notify it that
4
the MS has successfully completed the hard handoff. The target BS stops
5
timer T9.
6
m. The MSC sends a Clear Command to the source BS. The source BS stops
7
timer T306. The MSC starts timer T315.
8
n. The source BS sends a Clear Complete message to the MSC to notify it that
9
clearing has been accomplished. The MSC stops timer T315.
10
o. The target BS, upon detecting that the mobile has arrived from a different
11
packet zone, sends an In Traffic System Parameter Message to the mobile
12
indicating the current packet zone (CANID). The MS may acknowledge the
13
In-Traffic System Parameter Message by sending an MS Ack Order to the
14
target BS.
15
p. The MS detects a change in packet zone and sends an Enhanced Origination
16
Message to the target BS with DRS bit set to ‘0’.
17
q. The target BS acknowledges receipt of the Enhanced Origination Message by
18
sending a BS Ack Order to the MS.
19
r. The target BS sends an Additional Service Request message to the MSC. The
20
target BS starts timer T303.
21
s. The MSC sends an Assignment Request to the target BS and starts timer T10.
22
t. Upon receipt or the Assignment Request, the target BS stops timer T303. The
23
target BS sends an A9-Setup-A8 message, with Data Ready Indicator set to
24
‘0’, to the PCF. The handoff indicator of the A9 Indicators IE shall be set to 0.
25
The target BS starts timer TA8-Setup.
26
u. The target PCF establishes the A10/A11 link and the PDSN disconnects the
27
old A10/A11 link (see procedure in 3.11.5.5.10). (If the PDSN has data for the
28
mobile, it responds to the PCF with a Registration Reply message with the
29
Data Available Indicator in the Vendor/Organization Specific Extension.)
30
v. The PCF responds to the BS with an A9-Release A8 Complete message. The
31
BS stops timer TA8-Setup.
32
If the PDSN responds to the PCF with a Data Available Indicator, the PCF
33
responds to the BS with an A9-Connect-A8 message with Cause element set
34
to Data Ready to Send. In this case, the target BS may send a Call Assignment
35
Message to the MS to initiate activation of the packet data service. The target
36
BS will send a handoff direction message2 to the MS to invoke the additional
37
packet data service option. After Service Negotiation, the MS responds with a
38
Service Connect Completion Message. In this case, the remaining steps in this
39
scenario are ignored.
40
2 This may be a Handoff Direction Message, a General Handoff Direction Message, an Extended Handoff Direction Message, or a Universal Handoff Direction Message as appropriate.