37
_Change_Document_Information“ macro. 3G Call Flow 1 © Nokia Siemens Networks 2011 For internal use Unique document identifier (ID) / Version number / Life cycle status Dept. / Author / Date

3G Call Flow

Embed Size (px)

DESCRIPTION

3g Call flow description of NSN

Citation preview

Page 1: 3G Call Flow

_Change_Document_Information“ macro.

3G Call Flow

1 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 2: 3G Call Flow

RRC Connection Set up

RAB Set up

Radio Link Reconfiguration

2 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 3: 3G Call Flow

UE RNCNodeB CNRRC: RRC Connection Request (CCCH)

NBAP: Radio Link Setup Request

NBAP: Radio Link Setup Response

L1 Synchronization

3 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

RRC: RRC Connection Request (CCCH)

The Mobile user decides to initiate a voice call. The first message the UE will send on CCCH is RRC Connection Request. This will contain among other

things, Initial UE Identity and Establishment Cause.

Page 4: 3G Call Flow

RRC Connection Request UL

Start T300=400…8000ms

N300=0 to 7

4 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

CCCH : Common control channel :

bidirectional channel for transmitting the

control information Btw N/W and UE.

Page 5: 3G Call Flow

Slide 4

YG(-I1 Yadav, Gautam (NSN - IN/Noida), 3/11/2011

Page 6: 3G Call Flow

UE RNCNodeB CNRRC: RRC Connection Request (CCCH)

NBAP: Radio Link Setup Request

NBAP: Radio Link Setup Response

Cell ID, Frequency and SC

5 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

RRC: RRC Connection Setup (FACH)

RRC: RRC Connection Setup (CCCH)

RRC Connection Setup message is sent on CCCH with the parameters required to establish DCH. Also the state indicator will be set to DCH for the voice (or CS) call.

Page 7: 3G Call Flow

RRC CONNECTION SET UP

6 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / DateState Indicator and RNTI

A long UTRAN UE Identity is required

(U-RNTI, which includes SRNC Address) so

that the uplink message can be routed to

the Correct serving RNC.

RNTI: Radio N/W Temporary Identifier

Page 8: 3G Call Flow

UE RNCNodeB CNRRC: RRC Connection Request (CCCH)

NBAP: Radio Link Setup Request

NBAP: Radio Link Setup Response

RRC: RRC Connection Setup (FACH)

L1 Synchronization

NBAP: Synchronization IndicationT312= 1 to 15 N312 = 1 …..1000

7 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

RRC: RRC Connection Setup Complete (DCH)

RRC: RRC Connection Setup Complete (DCCH)

RRC Connection Setup complete will be sent on DCH. Ciphering related parameters and UE capability information will be sent back to SRNC.

L1 Synchronization

UE and Node are synchronized and DCH is allocated after L1 Synchronization.

Page 9: 3G Call Flow

RRC CONNECTION SET UP COMPLETE

8 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

This indicates wheather the message belongs to the

same signaling Procedure as the preceding setup

message.

The value Flag (0) indicates the transaction is initiated

by UE and this message is also from UE to RNC.

Supported Physical and transport channels

Frequency band

Page 10: 3G Call Flow

RRC: Initial Direct Transfer (MM: CM Service Request)SCCP: CR (Connection Request)

RANAP: Initial UE Message (MM: CM Service Request)

SCCP: CC (Connection Confirm)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RRC Connection Establishment – CELL DCH State

UE RNCNodeB CN

RRC: Initial Direct Transfer [CM Service Request]

9 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

RRC: Initial Direct Transfer [CM Service Request]

First NAS message is now sent by the UE. It indicates that a UE originated Voice call is required. The UE identity (TMSI) will also be passed in this message.

RRC: Downlink Direct Transfer [Authentication Request]

SRNC transfers the NAS message to the UE

RRC: Uplink Direct Transfer [Authentication Response]

UE computes the response (RES) and sends it back in the NAS message

Page 11: 3G Call Flow

MM CM SERVICE REQUEST

10 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 12: 3G Call Flow

RRC: Initial Direct Transfer (MM: CM Service Request)SCCP: CR (Connection Request)

RANAP: Initial UE Message (MM: CM Service Request)

SCCP: CC (Connection Confirm)

RANAP: Direct Transfer (MM: Authentication Request)

RRC: Downlink Direct Transfer (MM: Authentication Request)

RRC: Uplink Direct Transfer (MM: Authentication Response)

RRC Connection Establishment – CELL DCH State

UE RNCNodeB CN

RANAP: Direct Transfer (MM: Authentication Response)

11 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

RANAP: Security Mode Command

RRC: Security Mode Command

RRC: Security Mode Command

RRC Forwards the Security Mode command received from MSC/VLR to the UE.

RRC: Security Mode Complete

RRC: Security Mode Complete

RANAP: Security Mode Complete

Page 13: 3G Call Flow

SECURITY MODE COMMMAND

12 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 14: 3G Call Flow

SECURITY MODE COMMMAND COMPLETE

13 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 15: 3G Call Flow

UE RNCNodeB CN

RRC: Uplink Direct Transfer (CC: Setup)

RANAP: Direct Transfer (CC: Setup)

RANAP: Direct Transfer (CC: Call Proceeding)RRC: Downlink Direct Transfer (CC: Call Proceeding)

RRC: UL Direct Transfer [Setup]

14 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

The UE now sends the 'Setup' message in UL Direct Transfer message. This will include all the required parameters for setting up the voice call. It will include the number that UE wishes to be contacted and the bearer capability

Page 16: 3G Call Flow

CC SET UP

15 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 17: 3G Call Flow

MEASUREMENT REPORT

16 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 18: 3G Call Flow

ACTIVE CELL UPDATE AND COMPLETE

17 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 19: 3G Call Flow

RANAP: RAB Assignment RequestNBAP: Radio Link Reconfiguration Prepare

NBAP: Radio Link Reconfiguration Ready

NBAP: Radio Link Reconfiguration Commit)

< 1s

UE RNCNodeB CN

Different types of user data

Transferred on Iu Interface and

QOS for that.

(AC)

18 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

NBAP: Radio Link Reconfiguration Commit)

RRC: Radio Bearer Setup

RRC: Radio Bearer Setup Complete

RANAP: RAB Assignment Response

Timer wf_rb_setup_cpl (6s) is started when the RRC: Radio Bearer Setup message is sent to the UE In ca se the timer expires Iu Release Request is sent to the CN with release cause (radio_conn_lost)

wf_rb_setup_cpl (6s)radio_conn_lost

Page 20: 3G Call Flow

RADIO BEARER SET UP

19 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 21: 3G Call Flow

Call Established

RANAP: Direct Transfer (CC: Connect)RRC: Downlink Direct Transfer (CC: Connect)

RRC: Uplink Direct Transfer (CC: Connect Acknowledge)

RANAP: Direct Transfer (CC: Connect Acknowledge)

RRC: Uplink Direct Transfer (CC: Disconnect)

RANAP: Direct Transfer (CC: Disconnect)

RANAP: Location ReportRRC: Measurement Control

Call Disconnect

RANAP: Direct Transfer (CC: Alerting)RRC: Downlink Direct Transfer (CC: Alerting)

UE RNCNodeB CN

20 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

RANAP: Direct Transfer (CC: Release Complete)

RANAP: Iu Release Command

RANAP: Direct Transfer (CC: Disconnect)

RANAP: Direct Transfer (CC: Release)

RRC: Downlink Direct Transfer (CC: Release)

RANAP: Iu Release CompleteRRC: Downlink Direct Transfer (CC: RRC Connection Release)

RRC: Uplink Direct Transfer (CC: Release Complete)

NBAP: Radio Link Deletion Request

NBAP: Radio Link Deletion Response

ALCAP: ERQ (Establish Request)

ALCAP: ECF (Establish Confirm)

Page 22: 3G Call Flow

RRC State Transitions

21 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 23: 3G Call Flow

Transition from CELL_DCH to CELL_FACH

22 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 24: 3G Call Flow

Transition from CELL_FACH to CELL_DCH

23 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 25: 3G Call Flow

Transition from CELL_FACH to CELL_DCH

24 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 26: 3G Call Flow

Transition from CELL_DCH to CELL/URA_PCH

25 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 27: 3G Call Flow

Transition from CELL/URA_PCH to CELL_DCH

26 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 28: 3G Call Flow

Summary

27 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 29: 3G Call Flow

Signalling connection setup

28 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 30: 3G Call Flow

Signalling connection release

29 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Signalling connection release requested by the CN .

Page 31: 3G Call Flow

Signalling connection release

30 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Signalling connection release requested by the UE .

Page 32: 3G Call Flow

Paging the UE in idle mode

31 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

The RNC checks whether the paged UE is engaged in an ongoing radio resourcecontrol (RRC) connection. If there is no connection, the RNC starts the idle modepaging procedure.

Page 33: 3G Call Flow

Paging the UE in Connected mode

32 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Connected mode (CELL_FACH or CELL_DCH)

Page 34: 3G Call Flow

RNC-originated paging

33 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Page 35: 3G Call Flow

1. Cell update

Location updates

The UE message contains the cell update cause, which can be:

1. cell reselection2. periodic cell update3. uplink data transmission

34 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

3. uplink data transmission4. paging response5. re-entering service area6. radio link failure.

If the cell update was caused by cell reselection, the RNC updates the UE location information and resets the CELL_FACH or CELL_PCH state supervision timer.The RNC's confirmation message to the UE includes a radio network temporary identifier for the cell (C-RNTI) if the UE remains in CELL_FACH state.

Page 36: 3G Call Flow

2. URA update

When the UE is in URA_PCH state and has switched to a new URA, it sends anupdate message with the U-RNTI (radio network temporary identifier) and URAupdate cause to the RNC. The cause is either URA reselection or periodic URAupdate.

35 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date

Periodic URA update

Page 37: 3G Call Flow

THANKS

36 © Nokia Siemens Networks 2011

For internal useUnique document identifier (ID) / Version number / Life cycle status

Dept. / Author / Date