Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Mobile communication
SHAHBAZ JADOON(SP12-BTN-010)
Discuss the call setup process in 2G and 3G Networks? Draw a model by yourself in which
call setup process should be depicted (Step 1 to step N)?
Call Setup
Different procedures are necessary depending on the initiating and terminating party:
Mobile Originating Call MOC: Call setup, which are initiated by an MS
Mobile Terminating Call MTC: Call setup, where an MS is the called party
Mobile mobile Call MMC: Call setup between two mobile subscribers; MMC thus
consists of the execution of a MOC and a MTC one after the other.
o
Mobile Internal Call MIC: a special case of MMC; both MSs are in the same MSC
area, possibly even in the same cell.
o
o
o
Call setup
process in
3G
The steps to
establish an
MOC are as
follows:
Step 1: RRC connection setup between UE and SRNC
Step 2: Authentication and ciphering
Step 3: Radio access bearer establishment and call setup
Step 4: Call and Iu release
Figure 5-11 illustrates the interaction within UTRAN to establish an RRC connection between
the UE and the RNC. The process to set up a call begins with the UE sending an RRC connection
request over a CCCH (which is a RACH in the uplink direction). This message contains several
information elements, including IMSI or TMSI, LAI, RAI, and the reason for requesting the
RRC connection.
SRNC then synchronizes the frame protocol (FP) connection by sending an FP downlink sync
message. The RNC responds to the UE, indicating a successful RRC connection by sending an
RRC connection setup message. This message contains information elements such as transport
format, power control, and scrambling code. The UE responds with the RRC connection setup
complete to confirm the RRC connection establishment.
Step 2: Authentication and ciphering. On successful connection setup with the RNC, the UE
sends the RRC initial direct transfer message. This message is destined to the core network.
However, the RNC processes this partially, adds some more information needed to set up a call
and map it to the RANAP UE initial message. and sends it to the 3G MSC. The information
elements within this message carry information on UE identity, location, and connection setup
requirements. This message also indicates to the MSC and the RNC that a new signaling
relationship between the UE and CN needs to be established.
On receiving the service request from the UE, the MSC initiates the security procedures. This
includes the UE authentication and exchange of the encryption key. The MSC sends an
authentication request within the RANAP direct transfer message. The RNC maps and forwards
the authentication request message using RRC direct transfer to UE. The UE executes the
authentication algorithm and sends the result back in an authentication response message to the
MSC. As shown in Figure 5-12, this message is carried over as payload in the RRC direct
transfer and RANAP direct transfer messages. The RNC merely acts as a relay. Assuming that
the UE is successfully authenticated, the MSC then sends a security mode command to the RNC
indicating that the further transactions between the UE and the UTRAN should be encrypted.
The RNC in turn sends an RRC security mode command message to UE. The security mode
command message conveys the encryption algorithm and the encryption and integrity keys.
identifier. The UE responds with the radio bearer setup complete message. The RNC then sends
an RAB assignment response to the MSC. With this procedure successfully executed, there exists
a bearer to transport used data from the UE to the MSC.
The last action for the RNC is to clear the Iub interface resources.
The procedure is illustrated in Figure 5-15. The MSC sends an NBAP radio link deletion
message to the Node B. The Node B responds with a radio link deletion response message to
indicate the release of Iub interface resources.