3G Call Flow

By -
Here is UMTS subscriber call flow with the core network.

MS-A                                               MSC                                                      MS-B
****************************************************************************************************
-------Initial_UE(CM_SERVICE_REQ) -->|
------------Dir_Trnx(AUTH_REQ)         <--|
-------------Dir_Trnx(AUTH_RSP)         -->|
---------------SecurityModeCmd            <--|
--------------SecurityModeComp           -->|
-----Dir_Trnx(TMSI_RELOC_CMD)   <--|
----Dir_Trnx(TMSI_RELOC_COMP)  -->|
  -------------Dir_Trnx(SETUP)            -->|
---------Dir_Trnx(CALL_PROC)        <--|
----------------RabAssignReq               <--|
----------------RabAssignRsp               -->|

                                                                     |-->  PAGING  ---------------------------    
                                                                     |<--  Initial_UE(PAGE_RSP) -------------
                                                                     |-->  Dir_Trnx(AUTH_REQ)--------------        
                                                                     |<--  Dir_Trnx(AUTH_RSP)---------------        
                                                                     |-->  SecurityModeCmd -------------------       
                                                                     |<--  SecurityModeComp------------------        
                                                                     |-->  Dir_Trnx(TMSI_RELOC_CMD)------  
                                                                     |<--  Dir_Trnx(TMSI_RELOC_COMP) ---
                                                                     |-->  Dir_Trnx(SETUP)    -------------------       
                                                                     |<--  Dir_Trnx(CALL_CONF) --------------      
                                                                     |-->  RabAssignReq   ------------------------           
                                                                     |<--  RabAssignRsp  -------------------------            
                                                                     |<--  Dir_Trnx(CALL_ALERT)  -------------   
-----------Dir_Trnx(CALL_ALERT)       <--|
                                                                     |<--  Dir_Trnx(CALL_CONNECT)----------  
                                                                     |-->  Dir_Trnx(CALL_CONNECTACK)---- 
-------Dir_Trnx(CALL_CONNECT)     <--|
---Dir_Trnx(CALL_CONNECTACK)  -->|

 <--------------------------------------Call Connected at this stage---------------------------->
                                                                      |<--  Dir_Trnx(CALL_DISCONNECT) ------
                                                                      |-->  Dir_Trnx(CALL_REL)   ------------------     
                                                                      |<--  Dir_Trnx(CALL_RELCOMP)   ----------- 
 |<--   Dir_Trnx(CALL_DISCONNECT)---
|--  Dir_Trnx(CALL_REL)-------------------->    
                                                                      |-->  IuReleaseCmd    ---------------------------          
                                                                      |<--  IuReleaseComp    --------------------------         
--------Dir_Trnx(CALL_RELCOMP)     <--|
------------------IuReleaseCmd               <--|
------------------IuReleaseComp              -->|
*************************************************************************************************

Comments

Post a Comment

Popular posts from this blog

Intelligent Networks (IN) and CAMEL

By -
Image
Intelligent Networks (IN) :-  Intelligent Networks is a concept service intelligence resides in a central node called an SCP and SSPs (residing on Switches) relinquish control to this node at particular stages in a call so that appropriate service logic can be applied. Objectives of IN: - Increased Service Velocity / Speed of Deployment - Increased Range of Services - Evolvability from Existing Networks - Service & Vendor Independent Implementation - MSC just focuses on core job of call processing Network Before IN:   Before IN application, there was messed network for every node: Network with IN : After IN implementation, Network is organised. Basic Concepts  – PIC and DPs & BCSM: Point In Call (PIC)  :  A state in a basic call state model. Detection Point (DP)  :  A point in basic call processing at which specific event is detected. Detection Points represent  transitions  between points in call processing
Read more

Diameter Messages

By -
Capability Exchange: When two peers established transport connection, they must exchange the capability exchange message. this message allows the discovery of peer's identity and its capabilities. Once transport layer is established, CER and CEA exchanged to determine the capability of peer endpoint followed by DWR/DWA. In below example DiameterNodeA start diameter connection with DiameterNodeB after transport layer connection established. In case of TCP (Syn/Syn-Ack) and  SCTP (Init/Init-Ack/Coockie Echo) exchanged. In case of SCTP Connection establishment(CER, CEA, DWR, and DWA) are exchanged with setting out-of-order delivery false to avoid race-condition and for connection termination (DPR/DPA) set the timer to receive out-of-order message before terminating the connection.               DiameterNodeA                     DiameterNodeB                                     <------Transport Layer Established--------->                ---------------------- CER -------
Read more

SRVCC - Single Radio Voice Call Continuity

By -
SRVCC enables continuity of voice call anchored in IMS network, when UE changes its access network from packet based in eUTRAN to circuit based GERAN or UTRAN, without requiring the UE to have simultaneous access to both the radio network.   It accomplishes this by enhancing the MMEs, serving E-UTRAN and the 3GPP CS MSC serving GERAN/UTRAN such that when the UE is still anchored within the E-UTRAN network and triggers a measurement report indicating a need for handover (HO) to GERAN/UTRAN, the MSC can initiate IMS service continuity procedure towards the IMS domain in addition to preparing for a handover into its GERAN/UTRAN access, before the UE is directed to change its access network to GERAN/UTRAN.     The SRVCC feature requires the new Sv interface between MSC and MME. Sv Interface runs over UDP. Following messages are exchanged over Sv Interface:   - PS to CS Request - PS to CS Response - PS to CS Complete Notification - PS to CS Complete Acknowledge - PS t
Read more