Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Contents
Contents
7 Mobile Originated Call Establishment Procedure ..............................................................7-1
7.1 Overview.......................................................................................................................................................7-2
7.2 Normal Procedure .........................................................................................................................................7-2
7.2.1 Mobile Originated Call Establishment without OACSU (Early Assignment) .....................................7-2
7.2.2 Mobile Originated Call Establishment with OACSU (Late Assignment) ............................................7-6
7.2.3 Mobile Originated Call Establishment with OACSU (Very Early Assignment)..................................7-8
7.3 Internal Handling of BSC..............................................................................................................................7-9
7.4 Abnormal Procedures ....................................................................................................................................7-9
7.4.1 Abnormal Random Access/Immediate Assignment Procedure ..........................................................7-10
7.4.2 MSC directly delivers Disconnect to clear the call, instead of delivering the Assignment Request .. 7-11
7.4.3 Abnormal Assignment Procedure....................................................................................................... 7-11
7.4.4 Abnormal Procedure Cause by Call Interruption ...............................................................................7-12
7.4.5 Abnormal Procedure Caused by Hangup ...........................................................................................7-12
7.4.6 Abnormal Procedure Caused by MSC Clearing.................................................................................7-12
Issue 06 (2006-08-20)
Figures
Figures
Figure 7-1 Mobile originated call establishment without OACSU (early assignment) ......................................7-3
Figure 7-2 Mobile originated call establishment with OACSU (late assignment) .............................................7-6
Figure 7-3 Mobile originated call establishment with OACSU (very early assignment) ...................................7-8
ii
Issue 06 (2006-08-20)
Description
7.1 Overview
Issue 06 (2006-08-20)
7-1
7.1 Overview
Mobile originated call services include (excluding mobile-originated SMS)
z
MS calls MS
7-2
Issue 06 (2006-08-20)
Signaling procedure
Figure 7-1 Mobile originated call establishment without OACSU (early assignment)
BTS
MS
BSC
MSC
(3)
(6)
UA (7)
(9)
CC (10)
CM Service Accepted
(11)
Setup (12)
Call Proceeding (13)
Channel ACT (15)
(18)
UA (19)
(24)
DISC (32)
RLSD CMP
UA (33)
(40)
Step 1 MS sends a Channel Request message to BTS on the access channel (RACH) of Um interface.
The message contains the cause value "MOC", but that value is not completely accurate,
Issue 06 (2006-08-20)
7-3
because it is indicated both in the mobile originated call establishment procedure and IMSI
detach procedure.
Step 2 BTS sends a Channel Required message to BSC.
Step 3 Upon receipt of the Channel Required message, BSC allocates a signaling channel and sends
a Channel Activation message to BTS.
Step 4 If the channel type is correct, upon receipt of the Channel Activation message, BTS opens the
power amplifier on the specified channel, and sends a Channel Activation Acknowledge
message to BSC.
Step 5 BSC sends an Immediate Assignment Command message to MS via BTS. The message is
sent on AGCH on Um interface.
Step 6 MS sends an SABM frame on SDCCH to BTS to access the network.
Step 7 BTS returns a UA frame on SDCCH for acknowledgement.
Step 8 BTS sends an Establishment Indication message to BSC (This message contains the accurate
causes for MS access. For example, different cause values are indicated in the mobile
originated call establishment procedure and IMSI detach procedure). This message contains
the contents of the CM Service Request message.
Step 9 BSC establishes the SCCP link connection on A interface, and sends a CM Service Request
message to MSC.
Step 10 MSC returns a message to BSC to acknowledge the link connection.
Step 11 MSC sends a CM Service Accepted message to MS. The message is sent on SDCCH on Um
interface.
Step 12 The calling MS sends a Setup message on SDCCH.
Step 13 MSC sends a Call Proceeding message to the calling MS. The message is sent on SDCCH on
Um interface.
Step 14 MSC sends an Assignment Request message to BSC, which contains the CIC allocated to A
interface.
Step 15 BSC allocates a TCH, and sends a Channel Activation message to BTS.
Step 16 If the channel type is correct, upon receipt of the Channel Activation message, BTS opens the
power amplifier on the specified channel, starts to receive the uplink information and sends a
Channel Activation Acknowledge message to BSC.
Step 17 BSC sends an Assignment Command message to MS via BTS on SDCCH.
Step 18 MS sends an SABM frame to BTS, to access the network on FACCH indicated in the
Assignment Command message.
Step 19 BTS sends a UA frame for acknowledgement on FACCH.
Step 20 BTS sends an Establishment Indication message to BSC.
Step 21 After accessing the TCH, MS sends an Assignment Complete message to BSC on FACCH.
Step 22 After the radio traffic channel and terrestrial circuit are both successfully connected, BSC
sends an Assignment Complete message to MSC, and regards this call in session state.
Step 23 MSC sends an Altering message to the calling MS. The calling MS will hear the ringback
tone. The message is sent on FACCH on Um interface.
7-4
Issue 06 (2006-08-20)
Step 24 MSC sends a Connect message to MS. The message is sent on FACCH on Um interface.
Step 25 The calling MS returns a Connect Acknowledge message on FACCH to MSC.
Step 26 The calling MS and called MS enters the session state.
Step 27 After the conversation is over, the calling MS hangs up and sends a Disconnect message on
FACCH.
Step 28 MSC sends a Release message to MS. The message is sent on FACCH on Um interface.
Step 29 MS returns a Release Complete message. The message is sent on FACCH on Um interface.
Step 30 MSC sends a Clear Command message to BSC. Upon receipt of the message, BSC initiates
the release procedure. See Chapter 5 for the description of the subsequent release procedure.
Step 31 BSC sends a Channel Release message to MS through BTS, The message is sent on FACCH
on Um interface.
Step 32 MS sends DISC frame on FACCH.
Step 33 BTS returns UA frame on FACCH.
----End
Procedure explanation
Step 1 In Figure 7-1, 1~8 refer to the random access procedure and immediate assignment procedure.
In the two procedures, BSS allocates signaling channels to MS.
Step 2 Between 10~11, there may exist an authentication procedure, ciphering mode setting
procedure and classmark interrogation procedure (updating procedure).
Step 3 As per different data configuration of MSC, after the link connection is established on A
interface, MSC may not immediately deliver the CM Service Accepted message. Instead, it
may proceed as follows.
Step 4 Initiate the ciphering mode setting procedure by delivering a Cipher Mode Command (In that
case, MSC shall not deliver the CM Service Accepted message again).
Step 5 Initiate the authentication procedure by delivering an Authentication Request message.
Step 6 Initiate the classmark updating procedure by delivering a Classmark Update message.
Step 7 In addition, if [ECSC] in BSC data configuration is set to "Yes", the dual-band MS shall
report a Classmark Change message after it reports an Establishment Indication message.
Step 8 14~22 refer to the TCH assignment procedure.
In this procedure, BSS allocates the resources such as TCHs, A interface circuit, etc. to MS.
Step 9 30~40 refer to the release procedure.
The procedure shown in Figure 7-1 is a release procedure in which the calling MS first hangs
up. The logical channels on Um interface are released prior to the physical channels.
----End
Issue 06 (2006-08-20)
7-5
BSC
BTS
MSC
(5)
UA (6)
CM Service Accepted
(10)
Setup (11)
Call Proceeding (12)
Alerting
(13)
(20)
(22)
(23)
UA (32)
Deactive SACCH (33)
RLSD CMP
(39)
7-6
Issue 06 (2006-08-20)
Step 1 The difference between Figure 7-1 and Figure 7-2 is that late assignment takes place after the
Alerting indication is sent.
Step 2 The advantage of late assignment lies in that it can save the seizure time of TCHs.
Step 3 The disadvantage of late assignment is that if the subsequent assignment is unsuccessful, the
called MS can only hear the ring but cannot establish a connection, thus leading to user
complaints. Therefore, in actual application, this procedure is generally not adopted. Instead,
the procedure in Figure 7-1 is adopted.
----End
Procedure explanation
For relevant explanation, please refer to section 7.2.1 "Mobile Originated Call Establishment
without OACSU (Early Assignment)". The procedure in Figure 7-2 is a procedure in which
the calling MS first hangs up.
Issue 06 (2006-08-20)
7-7
BSC
BTS
MSC
(6)
UA (7)
UA (30)
Deactive SACCH(31)
Step 1 The difference between Figure 7-1 and Figure 7-3 is that the TCH allocated during the
immediate assignment in Figure 7-3 serves as a signaling channel. Therefore, no TCH need be
reallocated during the assignment procedure. Instead, the TCH allocated in the immediate
assignment procedure is adjusted as a TCH by using the Mode Modify message.
7-8
Issue 06 (2006-08-20)
Step 2 Very early assignment generally takes place if there is no free SDCCH for allocation during
immediate assignment, but there are free TCHs and immediate assignment of TCHs is
allowed in BSC data configuration.
----End
Procedure explanation
For relevant explanation, please refer to 7.2.1 "Mobile Originated Call Establishment
without OACSU (Early Assignment)." The procedure in Figure 7-3 is a procedure in which
the calling MS first hangs up.
Issue 06 (2006-08-20)
7-9
Because there are various causes for abnormal procedures, here, merely the common cases are
described.
7-10
Issue 06 (2006-08-20)
The boards and their respective backplanes and optical fiber that are related to the
inter-module communication in BSC, such as GMC2, GMCC, GSNT, GOPT and GFBI.
The boards related to A interface, such as E3Ms, TCSMs and their backplanes
Issue 06 (2006-08-20)
7-11
Directed Retry
Because there is no appropriate TCH for allocation, and the direct re-attempt permit switch is
set to "On" in BSC data configuration, upon receipt of an Assignment Request message from
MSC, BSC shall initiate handover (with the cause value "Directed retry) as per the actual
situation, so that MS can directly attempt to access other cells.
7-12
Issue 06 (2006-08-20)
Issue 06 (2006-08-20)
7-13