17.04.2015 Views

RANAP Signaling in UMTS Call PDF - EventHelix.com

RANAP Signaling in UMTS Call PDF - EventHelix.com

RANAP Signaling in UMTS Call PDF - EventHelix.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

-ranap Interfaces (Orig<strong>in</strong>at<strong>in</strong>g <strong>Call</strong>)<br />

UTRAN<br />

RNC<br />

Core Network<br />

MSC/VLR<br />

EventStudio System Designer 6<br />

06-Oct-13 07:43 (Page 1)<br />

A 3G-<strong>UMTS</strong> orig<strong>in</strong>at<strong>in</strong>g call is described here. Setup radio bearers and <strong>RANAP</strong> signal<strong>in</strong>g are covered <strong>in</strong> detail. You can click<br />

on most <strong>RANAP</strong> messages to see the full content of the message.<br />

This call flow has been generated with from a Wireshark PCAP file us<strong>in</strong>g VisualEther (http://www.eventhelix.<strong>com</strong>/VisualEther/).<br />

The generated call flow was later modified with EventStudio (http://www.eventhelix.<strong>com</strong>/EventStudio/) to add <strong>com</strong>ments and<br />

term<strong>in</strong>al level <strong>in</strong>teractions.<br />

DTAP MM CM Service Request<br />

ranap<br />

ranap<br />

BCD Digits : 123456780000000<br />

Core Network decides that the term<strong>in</strong>al needs to be<br />

authenticated.<br />

The CM Service Request is the first message to be received for<br />

the call from the RNC. This message also sets up the SCCP<br />

connection between the RNC and the Core Network.<br />

The "CM Service Request" also marks the start of an Iu<br />

connection.<br />

DTAP MM Authentication Request<br />

ranap<br />

ranap<br />

DTAP MM Authentication Response<br />

ranap<br />

ranap<br />

ranap<br />

<strong>RANAP</strong> CommonID<br />

ranap<br />

id : id-PermanentNAS-UE-ID (23)<br />

IMSI is sent to the RNC.<br />

Core Network sends new keys for cipher<strong>in</strong>g and <strong>in</strong>tegrity<br />

protection.<br />

ranap<br />

Security Mode Command<br />

ranap<br />

UIAs,<br />

IK,<br />

UEAs,<br />

CK<br />

Core Network <strong>in</strong>itiates cipher<strong>in</strong>g and <strong>in</strong>tegrity Protection. The<br />

"MSC/VLR" sends the Security Mode Command message to<br />

RNC.<br />

ranap<br />

Security Mode Complete<br />

ranap<br />

DTAP MM CM Service Accept<br />

ranap<br />

ranap<br />

The Core Network accepts the service request.<br />

ranap<br />

DTAP CC Setup<br />

ranap<br />

.... 0001 = Number<strong>in</strong>g plan identification<br />

: ISDN /Telephony Number<strong>in</strong>g (Rec ITU<br />

-T E.164) (0x01),<br />

BCD Digits : 5<br />

<strong>Call</strong> Setup request is received from the RNC.<br />

DTAP CC <strong>Call</strong> Proceed<strong>in</strong>g<br />

ranap<br />

ranap<br />

ranap<br />

<strong>RANAP</strong> RAB -Assignment<br />

ranap<br />

id : id -RAB -SetupOrModifiedList (52),<br />

id : id -RAB -SetupOrModifiedItem (51),<br />

id : id -Ass -RAB -Parameters (90)<br />

"Core Network" signals that the call setup is proceed<strong>in</strong>g.<br />

RNC responds to Core Network after <strong>com</strong>plet<strong>in</strong>g RB Setup with<br />

the Term<strong>in</strong>al.<br />

ranap<br />

DTAP CC Alert<strong>in</strong>g<br />

ranap<br />

Ask RNC to Notify the term<strong>in</strong>al that the subscriber is ber<strong>in</strong>g<br />

rung.<br />

ranap<br />

DTAP CC Connect<br />

ranap<br />

Notify the RNC that the called subscriber has answered.


-ranap Interfaces (Orig<strong>in</strong>at<strong>in</strong>g <strong>Call</strong>)<br />

UTRAN<br />

Core Network<br />

RNC<br />

MSC/VLR<br />

DTAP CC Connect Acknowledge<br />

ranap<br />

ranap<br />

EventStudio System Designer 6<br />

06-Oct-13 07:43 (Page 2)<br />

RNC responds back with <strong>com</strong>pletion of connect.<br />

ranap<br />

DTAP CC Disconnect<br />

ranap<br />

.001 0000 = Cause : (16) Normal call<br />

clear<strong>in</strong>g<br />

RNC sends call disconnect to the Core Network.<br />

ranap<br />

DTAP CC Release<br />

ranap<br />

Core Network releases the session.<br />

DTAP CC Release Complete<br />

ranap<br />

ranap<br />

RNC signals release <strong>com</strong>plete to Core Network<br />

ranap<br />

<strong>RANAP</strong> Iu-Release<br />

ranap<br />

Core Network <strong>in</strong>itiates the Iu release.<br />

id : id -Cause (4)<br />

ranap<br />

<strong>RANAP</strong> Iu-Release<br />

ranap<br />

RNC signals back the release of the Iu connection.<br />

This call flow has been generated with from a Wireshark PCAP file us<strong>in</strong>g VisualEther (http://www.eventhelix.<strong>com</strong>/VisualEther/).<br />

The generated call flow was later modified with EventStudio (http://www.eventhelix.<strong>com</strong>/EventStudio/) to add <strong>com</strong>ments and<br />

term<strong>in</strong>al level <strong>in</strong>teractions.<br />

Explore more call flow diagrams at: http://www.eventhelix.<strong>com</strong>/realtimemantra/tele<strong>com</strong>/

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!