Você está na página 1de 6

3.1.2.

10 T3107 expiry

This section is not applicable to the VGCH Normal Assignment.


T3107 is started by the BSC after it has sent to the MS (transparently via the BTS) the ASSIGNMENT
COMMAND message. When it expires, the understanding of the Alcatel BSS system is that the MS is
no longer connected (lost) to the BSS. In this case the BSC sends to the MSC an ASSIGNMENT
FAILURE message with the special cause "Radio interface message failure", clears the call - see
ref.[13] A0500 - and starts timer T9110 - see section 3.1.2.11 on T9110 expiry.
The BSC puts the A interface circuit associated to the assignment into IDLE state and expects the
MSC to clear the call (i.e. send a CLEAR COMMAND message).
If T3107 has expired, whilst T9110 is running, the BSC’s behaviour is as follows:
Case a): If the BSC receives from the MSC the CLEAR COMMAND message, on the same
SCCP connection, to clear the call as a response to the ASSIGNMENT FAILURE
message, it will respond with CLEAR COMPLETE message and then will await the
SCCP release sequence, which is initiated by the MSC and consists of a SCCP
RELEASED (RLSD) message followed by a SCCP RELEASE COMPLETE (RLC)
message (Figure 17).
Case b): If the BSC receives from the MSC, on the same SCCP connection, another
ASSIGNMENT REQUEST message, it will send an ASSIGNMENT FAILURE
message with cause "Radio interface message failure" without restarting T9110 - see
ref.[13] A0900 (Figure 18).
Case c): If the MSC reuses the same A interface circuit by sending, on another SCCP
connection, a new ASSIGNMENT REQUEST message, the BSC will accept the
request and perform the Normal Assignment procedure as normally (Figure 19).

ED 04 RELEASED NORMAL ASSIGNMENT

EVOLIUM 3BK 11202 0438 DSZZA 36/115


0438_04.doc
2006/03/31
Case a) T3107 expiry followed by clearing initiated by the MSC

MS BTS BSC MSC MSC


(SCCP 1) (SCCP 2)
(1) || || || ASSIGNMENT REQ(CICn) || ||
(1) || || || <------------------------- || ||
(1) || || PHYSICAL CONTEXT REQ || || ||
(1) || || <------------------------- start T9108 || ||
(1) || || PHYSICAL CONTEXT CNF || || ||
(1) || || ------------------------> stop T9108 || ||
(1) || || CHANNEL ACTIVATION (TCH) || ||
(1) || || <--------------------------------start T9103 || ||
(1) || || CHANNEL ACTIVATION ACK || || ||
(1) || || -------------------------------->stop T9103 || ||
(2) || ASSIGN CMD || DR (ASSIGNMENT CMD) || || ||
(2) || <-------------------- || <--------------------------------start T3107 || ||
(2) || RR STATUS || RR STATUS || || ||
(2) || --------------------> || ---------------------------------> || || ||
(2) || || || || ||
(3) || || T3107 exipy || ||
(3) || || || ASSIGNMENT FAILURE || ||
(3) || || || ---------------------------> || ||
(3) || || || || ||
(3) || || CICn is put into IDLE state by BSC || ||
(4) || || || || ||
(4) || || start T9110 || ||
(4) || || || || ||
(5) || || || CLEAR COMMAND || ||
(5) || || || <---------------------------- || ||
(5) || || stop T9110 || ||
(5) || || || CLEAR COMPLETE || ||
(5) || || || ---------------------------> || ||
(5) || || start T9101 || ||
(5) || || || RLSD || ||
(5) || || || <---------------------------- || ||
(5) || || stop T9101 || ||
(5) || || || RLC || ||
(5) || || || ----------------------------> || ||

Figure 17 : T3107 expiry (case a)

Note: Atermux nibble TIC connection procedure is not shown here. Please refer to Figure 1.

1 The MSC initiates the Normal assignment procedure.
The BSS initiates and completes the Physical context and Channel activation procedures
successfully.
2 The ASSIGNMENT COMMAND message is sent to the MS and timer T3107 is started.
The MS finds an error in the message and returns a RR STATUS message to the BSS (the MS
may not respond).
The BSS discards the RR STATUS message and awaits the completion of the Assignment
procedure.
3 Timer T3107 expires and the ASSIGNMENT FAILURE message is sent to the MSC (with the
cause “Radio interface message failure”). The BSC puts the A interface circuit associated to the
assignment into IDLE state..
4 The BSS releases the SDCCH and TCH as specified in ref.[13] A0500 (note that these
scenarios are not shown here to simplify the message sequence chart) and starts timer T9110 to
supervise the response from the MSC.
5 The MSC sends the CLEAR COMMAND message to clear the call as a response to the
ASSIGNMENT FAILURE message.
The BSC responds with CLEAR COMPLETE message and then awaits the SCCP release

ED 04 RELEASED NORMAL ASSIGNMENT

EVOLIUM 3BK 11202 0438 DSZZA 37/115


0438_04.doc
2006/03/31
sequence, which is initiated by the MSC and consists of a SCCP Released (RLSD) message
followed by a SCCP Release complete (RLC) message.

Case b) Refusal of all ASSIGNMENT REQUEST messages (on the same SCCP connection)
after T3107 expiry

MS BTS BSC MSC MSC


(SCCP 1) (SCCP 2)
(1) || || || ASSIGNMENT REQ(CICn) || ||
(1) || || || <------------------------- || ||
(1) || || PHYSICAL CONTEXT REQ || || ||
(1) || || <------------------------- start T9108 || ||
(1) || || PHYSICAL CONTEXT CNF || || ||
(1) || || ------------------------> stop T9108 || ||
(1) || || CHANNEL ACTIVATION (TCH) || ||
(1) || || <--------------------------------start T9103 || ||
(1) || || CHANNEL ACTIVATION ACK || || ||
(1) || || -------------------------------->stop T9103 || ||
(1) || ASSIGN CMD || DR (ASSIGNMENT CMD) || || ||
(1) || <-------------------- || <--------------------------------start T3107 || ||
(1) || RR STATUS || RR STATUS || || ||
(1) || --------------------> || ---------------------------------> || || ||
(1) || || || || ||
(2) || || T3107 exipy || ||
(2) || || || ASSIGNMENT FAILURE || ||
(2) || || || ---------------------------> || ||
(2) || || || || ||
(2) || || CICn is put into IDLE state by BSC || ||
(2) || || || || ||
(2) || || start T9110 || ||
(2) || || || || ||
(3) || || || ASSIGNMENT REQ || ||
(3) || || || <---------------------------- || ||
(3) || || || ASSIGNMENT FAILURE || ||
(3) || || || ---------------------------> || ||

Figure 18 : T3107 expiry (case b)

Note: Atermux nibble TIC connection procedure is not shown here. Please refer to Figure 1.

1 The Normal assignment procedure is initiated and the MS sends the RR STATUS message.
Note that the MS may not respond with the RR STATUS message but simply discard the
ASSIGNMENT COMMAND message.
If the RR STATUS message is sent, the BSC discards the message.
2 T3107 expires and the BSC carries out a Call release scenario with SDCCH and TCH and
sends an ASSIGNMENT FAILURE message (cause "Radio interface message failure") to the
MSC; puts the A interface circuit associated to the assignment into IDLE state and starts timer
T9110.
3 The MS is either in the process of being released or already released by the BSS. If the BSS
receives from the MSC, on the same SCCP connection (SCCP1), another ASSIGNMENT
REQUEST message it responds with an ASSIGNMENT FAILURE message (cause "Radio
interface message failure"). See section 3.1.2.11 on T9110 expiry for the scenario, which follows
this one.

ED 04 RELEASED NORMAL ASSIGNMENT

EVOLIUM 3BK 11202 0438 DSZZA 38/115


0438_04.doc
2006/03/31
Case c) Acceptance of another ASSIGNMENT REQUEST message (with the same CIC) on
another SCCP connection

MS BTS BSC MSC MSC


(SCCP 1) (SCCP 2)
(1) || || || ASSIGNMENT REQ(CICn) || ||
(1) || || || <------------------------- || ||
(1) || || PHYSICAL CONTEXT REQ || || ||
(1) || || <------------------------- start T9108 || ||
(1) || || PHYSICAL CONTEXT CNF || || ||
(1) || || ------------------------> stop T9108 || ||
(1) || || CHANNEL ACTIVATION (TCH) || ||
(1) || || <--------------------------------start T9103 || ||
(1) || || CHANNEL ACTIVATION ACK || || ||
(1) || || -------------------------------->stop T9103 || ||
(1) || ASSIGN CMD || DR (ASSIGNMENT CMD) || || ||
(1) || <-------------------- || <-------------------------------- start T3107 || ||
(1) || RR STATUS || RR STATUS || || ||
(1) || --------------------> || ---------------------------------> || || ||
(1) || || || || ||
(2) || || T3107 exipy || ||
(2) || || || ASSIGNMENT FAILURE || ||
(2) || || || ---------------------------> || ||
(2) || || || || ||
(2) || || CICn is put into IDLE state by BSC || ||
(2) || || || || ||
(2) || || start T9110 || ||
(2) || || || || ||
(3) || || || ASSIGNMENT REQ(CICn) ||
(3) || || (accepted by the BSC) || <---------------------------------------------------------------- ||
(3) || || stop T9110 || ||
(3) || || || || ||

Figure 19 : T3107 expiry (case c)

Note: Atermux nibble TIC connection procedure is not shown here. Please refer to Figure 1.

1 The Normal assignment procedure is initiated and the MS sends the RR STATUS message.
Note - the MS may not respond with the RR STATUS message but simply discard the
ASSIGNMENT COMMAND.
If the RR STATUS message is sent the BSC discards the message.

2 T3017 expires and the BSC carries out a call release scenario with SDCCH and TCH channels
and sends an ASSIGNMENT FAILURE (cause "Radio interface message failure") to the MSC;
puts the A interface circuit associated to the assignment into IDLE state and starts T9110.

3 The MS is either in the process of being released or already released by the BSS. If the BSS
receives from the MSC, on another SCCP connection (SCCP2), a new ASSIGNMENT
REQUEST reusing the same A interface circuit, the BSC will accept the request and perform the
Normal Assignment procedure as normally.

ED 04 RELEASED NORMAL ASSIGNMENT

EVOLIUM 3BK 11202 0438 DSZZA 39/115


0438_04.doc
2006/03/31
3.1.2.11 T9110 expiry

This section is not applicable to the VGCH Normal Assignment.


Timer T9110 is run by the BSC if an ASSIGNMENT FAILURE message has been sent to the MSC as
a consequence of timer T3107 expiring during a Normal assignment procedure - see section 3.1.2.10
on T3107 expiry.
The function of the timer is to ensure that the connection is eventually cleared by the MSC or BSS.
When T3107 expires, SDCCH and TCH are released - see ref.[13] A0500. This leaves only the SCCP
connection active.
When, and if, T9110 expires, the Call release scenario specified in ref.[13] A0600 occurs.
The following message sequence chart shows the behaviour of the BSC when the MSC does not start
to clear within the period set by the T9110 timer.
No MSC release, T9110 expires
MS BTS BSC MSC
_____________________________________________________________________________________
(1) || || | | DT1 (ASSIGNMENT REQ)
(1) || || | | <---------------------------- | |
(1) || | | PHYSICAL CONTEXT REQ || ||
(1) || | | <--------------------------------------------- start T9108 ||
(1) || | | PHYSICAL CONTEXT CNF || ||
(1) || | | ---------------------------------------------> stop T9108 ||
(1) || || CHANNEL ACTIVATION || ||
(1) || | | <--------------------------------------------- start T9103 ||
(1) || | | CHANNEL ACTIVATION ACK || ||
(1) || | | ---------------------------------------------> stop T9103 ||
(1) || ASSIGN CMD | | DR (ASSIGNMENT CMD) | | ||
(1) | | <---------------------------- | | <--------------------------------------------- start T3107 ||
(1) | | RR STATUS | | RR STATUS || ||
(1) | | ----------------------------> | | ---------------------------------------------> | | ||
(1) || || || ||
(1) || || T3107 expiry ||
(1) || || | | DT1 (ASSIGNMENT FAILURE)
(1) || || | | ----------------------------> | |
(2) || || CIC is put into IDLE state by BSC | |
(2) || || start T9110 ||
(2) | | || || ||
(2) || || || ||
(3) || || T9110 expiry ||
(3) || || | | RLSD ||
(3) || || | | ----------------------------> | |
(3) || || || RLC ||
(3) || || | | <---------------------------- | |

Figure 20 : T9110 expiry

Note: Atermux nibble TIC connection procedure is not shown here. Please refer to Figure 1.

1 The Normal assignment is initiated by the MSC. The MS finds a fault with the ASSIGNMENT
COMMAND message and returns an RR STATUS message, which is discarded by the BSS.
2 The BSC puts the A interface circuit associated to the assignment into IDLE state and starts
timer T9110 to await the response from the MSC (i.e. CLEAR COMMAND message). The BSC
releases TCH and SDCCH.
3 T9110 expires, the SCCP connection is released by sending the SCCP Released (RSLD)
message - see ref.[13] A0600.
Note that the sending of the RLSD message is a speciality of the Alcatel BSS. It is the only

ED 04 RELEASED NORMAL ASSIGNMENT

EVOLIUM 3BK 11202 0438 DSZZA 40/115


0438_04.doc
2006/03/31
method with which the Alcatel BSS may clear the SCCP connection and release the resources
associated with it.
Note also that some MSCs may not send the RLC message as a response, however the BSS
will release the resources in any case.

3.2 DETAILED BEHAVIOUR WITHIN BSS ENTITIES

3.2.1 BTS behaviour

3.2.1.1 BTS old channel behaviour

The BTS old channel is completely unaware that the Normal assignment procedure is taking place.
There is no specific behaviour to be performed by the BTS on the old channel.

3.2.1.2 BTS new channel behaviour

Upon receipt of the CHANNEL ACTIVATION message,


• If the BTS is in TDM mode, it starts sending TRAU frames to the transcoder. The TRAU frames
sent by the BTS depend on the codec, channel rate and channel type that will be used on this
traffic path. On reception of the TRAU frames from the BTS, the TRAU will set its mode of
operation according to the information coded in the control bits. It then starts sending downlink
frames.
• If the BTS is in IP mode, it sends uplink TRAUP packets with the destination Address (TIC) of the
TRAU and own address (downlink address). Additionally it attaches the appropriate uplink control
IE and uplink extended control IE. On reception of the uplink TRAUP packets, the TRAU
immediately starts sending downlink TRAUP packets according to the service requested in uplink.
• If the call is an AMR or an AMR WB speech call, the BTS uses the start mode (implicit or explicit,
as indicated in CHANNEL ACTIVATION message) as the intial codec mode. See ref.[8] for details.
In conflict situations within the BTS (i.e. CHANNEL ACTIVATION messages indicating SDCCH for
timeslots configured as TCH, or vice versa), the BTS follows the BSC request.
If the requested channel (TCH or SDCCH or VGCH) in CHANNEL ACTIVATION message is already
activated in the BTS, the BTS shall first release this busy channel (resource state mismatch between
BTS and BSC - see ref.[13] N1500).
Once the channel is activated, ciphering is immediately started (if applied) of any frames sent to the
radio interface and the transmission of the appropriate SYSTEM INFORMATION TYPE 5 family
messages as well as the appropriate SYSTEM INFORMATION TYPE 6 message is started on the
Downlink SACCH.
The Layer 1 timing advance is used if supplied, otherwise the timing advance will indicate the GSM
invalid value. This will be updated when the BTS has calculated the timing advance of the MS on the
new channel.
For point-to-point calls, upon receipt of the RL ESTABLISH INDICATION message from the BTS
Layer 2, the BTS Layer 3 sends the ESTABLISH INDICATION message to the BSC, starts T_CFI_TR
and starts the TA computation. While T_CFI_TR is running, transcoder alarms are ignored by the
BTS.

ED 04 RELEASED NORMAL ASSIGNMENT

EVOLIUM 3BK 11202 0438 DSZZA 41/115


0438_04.doc
2006/03/31